View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001463 | T99X171.00 SKB Eagle | SW Issue | public | 2022-04-13 15:53 | 2022-11-04 13:47 |
| Reporter | (ALTech) Younkwang Jung | Assigned To | (ALTech) Younkwang Jung | Due Date | |
| Priority | normal | Severity | s4-minor | Reproducibility | have not tried |
| Status | closed | Resolution | not fixable | ||
| Summary | 0001463: [Smart3][VoC] About VoC log (!!! FAILED BINDER TRANSACTION !!! ) | ||||
| Description | Hi Kerwin The following string was observed during the analysis of the Voc log: 04-05 20:21:00.900 E 4563 6217 JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 1056768) https://jira.skbroadband.com/browse/BFXBTF-453 In SPTEK, SPTEK no longer check because the log is from gms. Please check why this log is observed. Thank you YK.Jung | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) JunGyu Kim , (ALTech) SY Yoon , |
|---|
|
|
|
|
|
Hi YK, If this log is from GMS, we don't have source code to investigate it. Do you know how to reproduce it? As far as you know, before posting this question to Google issue tracker. We should collect enough information as follows, Description Field MUST provide the details of the issue ● Testing environment ○ Android OS version ○ SW configuration (reversion of relevant APKs, etc) ○ HW configuration (refer to your Project Tracker HW matrix) ○ Environment details as relevant (region, language, network setup) ● Steps to reproduce the issue ● Expected and actual results ● Failure rate ● Reproducibility on an SOC reference design, Android TV developer device (ADT-X) or other in-market Android TV devices ● Bug report ○ Highlight via text snippet any relevant error messages to aid investigation |
|
|
Hi Jason If I do google-reset on Smart3, and stay still, this log is being observed. Can you check if you can see this log even after google-reset in the Amlogic reference? Thank you YK.Jung |
|
|
Hi YK, I did Google reset on Amlogic ref board, I can see the following logs, 130|franklin:/ $ logcat -s JavaBinder GmsClient --------- beginning of main --------- beginning of system 07-15 10:12:23.021 4814 5395 E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 388) 07-15 10:12:23.022 4814 5395 W GmsClient: IGmsServiceBroker.getService failed 07-15 10:12:23.022 4814 5395 W GmsClient: android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died 07-15 10:12:23.022 4814 5395 W GmsClient: at android.os.BinderProxy.transactNative(Native Method) 07-15 10:12:23.022 4814 5395 W GmsClient: at android.os.BinderProxy.transact(BinderProxy.java:510) 07-15 10:12:23.022 4814 5395 W GmsClient: at lhj.c(:com.google.android.gms@212621097@21.26.21 (080306-387928701):5) 07-15 10:12:23.022 4814 5395 W GmsClient: at lfl.u(:com.google.android.gms@212621097@21.26.21 (080306-387928701):13) 07-15 10:12:23.022 4814 5395 W GmsClient: at kpc.run(:com.google.android.gms@212621097@21.26.21 (080306-387928701):5) 07-15 10:12:23.022 4814 5395 W GmsClient: at android.os.Handler.handleCallback(Handler.java:883) 07-15 10:12:23.022 4814 5395 W GmsClient: at android.os.Handler.dispatchMessage(Handler.java:100) 07-15 10:12:23.022 4814 5395 W GmsClient: at vlk.gE(:com.google.android.gms@212621097@21.26.21 (080306-387928701):0) 07-15 10:12:23.022 4814 5395 W GmsClient: at vlk.dispatchMessage(:com.google.android.gms@212621097@21.26.21 (080306-387928701):10) 07-15 10:12:23.022 4814 5395 W GmsClient: at android.os.Looper.loop(Looper.java:214) 07-15 10:12:23.022 4814 5395 W GmsClient: at android.os.HandlerThread.run(HandlerThread.java:67) Then, I updated all apps from Google Play Store and reboot device, I don't see any logs related to JavaBinder anymore. Thanks, Jason |
|
|
Hi Jason I don't think that we need to consider this issue any more. I'll close this issue. Thanks YK.Jung |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-04-13 15:53 | (ALTech) Younkwang Jung | New Issue | |
| 2022-04-13 15:53 | (ALTech) Younkwang Jung | Status | new => assigned |
| 2022-04-13 15:53 | (ALTech) Younkwang Jung | Assigned To | => (SW) Kerwin Chen |
| 2022-04-13 15:53 | (ALTech) Younkwang Jung | File Added: 28_CD_C4_FA_BA_0B_20220406144249.zip | |
| 2022-04-13 15:55 | (ALTech) Younkwang Jung | Issue Monitored: (SW) Brent Choi | |
| 2022-04-13 15:55 | (ALTech) Younkwang Jung | Issue Monitored: (SW) Kerwin Chen | |
| 2022-04-13 15:55 | (ALTech) Younkwang Jung | Issue Monitored: (ALTech) SY Yoon | |
| 2022-04-13 15:55 | (ALTech) Younkwang Jung | Issue Monitored: (ALTech) JunGyu Kim | |
| 2022-04-14 14:32 | (SW) Kerwin Chen | Assigned To | (SW) Kerwin Chen => (SW) Jason Ling |
| 2022-04-14 14:56 |
|
Note Added: 0009882 | |
| 2022-04-14 14:57 |
|
Assigned To | (SW) Jason Ling => (ALTech) Younkwang Jung |
| 2022-05-25 09:08 | (ALTech) Younkwang Jung | Note Added: 0010069 | |
| 2022-07-15 10:30 |
|
Note Added: 0010386 | |
| 2022-11-04 13:47 | (ALTech) Younkwang Jung | Note Added: 0011164 | |
| 2022-11-04 13:47 | (ALTech) Younkwang Jung | Status | assigned => closed |
| 2022-11-04 13:47 | (ALTech) Younkwang Jung | Resolution | open => not fixable |
